Database setup for Oracle 11g R2

Database creation

The Project Portal database must be created from the database template supplied with Project Portal (in the mpp2012dbsetup package). To start the setup of a Project Portal database, perform the following tasks:

• Extract and place the mpp2012_oracle11.2.0.3_vxx.dbt database template into $ORACLE_HOME/assistants/dbca/templates depending on your Oracle version.
• Start the Oracle Database Configuration Assistant (dbca) and start creation of a new database based on the Project Portal template appropriate for your Oracle version (mpp2012_oracle11.2.0.3_vxx)

The following settings are mandatory for the newly created database. BlueCielo ECM Solutions must confirm possible changes to these settings:

• Set the database type to Oracle Single Instance Database (Oracle Real Application Cluster is not supported by Project Portal)
• Configure the database with Enterprise Manager enabled (to ease database management)
• File System Storage
• Disable ARCHIVELOG unless you are familiar with Oracle database backups and have procedures for cleaning up archive files in place
• Database components:
  • Oracle Text
  • Enterprise Manager Repository

• Allocate as much memory to Oracle as possible during database creation based on the amount of physical memory available and services running on the database server.

  If the server has less than 10GB of memory, use Oracle Automatic Memory Management and set the MEMORY_TARGET and MAX_MEMORY_TARGET variables according to the Oracle documentation while maximizing memory allocated to the database.

  If the server has more than 10GB of memory, we highly recommend using HugePages. When setting memory variables, it should be noted that the SGA size (SGA_MAX_SIZE) should be at least 10% of the size of the database, including indexes. See the Oracle documentation on memory management and HugePages.

• The database character set to use for Project Portal 2015 databases is AL32UTF8
• Multiplex redo log and control files according to file system fault tolerance.

For security reasons, the Oracle Listener should be configured to bind to the localhost (127.0.0.1) interface when Project Portal and Oracle are running on the same server. When Project Portal and Oracle are on different servers, we recommend blocking traffic to the Oracle server from sources other than the Project Portal server.

For detailed information about Oracle database setup, see Oracle database configuration.

We recommend that a plustrace role be created to grant access to Oracle Dynamic Performance Tables. This helps in tuning the database and recognizing possible bottlenecks in query performance. To create the role, run the following command while the database is running:

sqlplus / as sysdba < $ORACLE_HOME/sqlplus/admin/plustrce.sql

Setting up database schema for Project Portal

Once the database has been created, the Project Portal user account needs to be created with specific access rights. The script kronouser.sql creates the user kronodoc with the password kronodoc. These may be changed by editing the kronouser.sql script as follows.

sqlplus / as sysdba < <Path to kronodbsetup/kronorole.sql>
sqlplus / as sysdba < <Path to kronodbsetup/kronouser.sql>

For detailed information about Oracle database user setup, see Oracle database configuration.

Post-installation tuning

Certain database parameters such as memory allocation parameters should be tuned after the system has been running in production for 1 to 2 weeks. You can use the Oracle Automatic Database Diagnostic Monitor (ADDM) to get advice on tuning these parameters. Use of these tools requires appropriate licenses that can be purchased to supplement Oracle Enterprise Edition. ADDM is not licensed with Oracle Standard edition.